Methods for Enforcing Limited Mobility in Mobile Network

ABSTRACT

Systems, methods, and instrumentalities are disclosed for enforcing limited mobility in a mobile network. For example, a wireless transmit/receive unit (WTRU) may receive (e.g., receive from a network) a mapping of physical cell identifications (PCIs) to area identifications (AIDs). The WTRU may determine a first PCI associated with a first neighbor cell. The WTRU may determine, based on the first PCI and the PCIs to AIDs mapping, whether the WTRU is allowed to access the first neighbor cell. The WTRU may perform cell selection or reselection with the first neighbor cell as a cell selection or reselection candidate. The WTRU may perform cell selection or reselection based on the WTRU determining that the WTRU is allowed to access the first neighbor cell. The WTRU may determine that the WTRU is allowed to access the first neighbor cell based on the first PCI and the PCIs to AIDs mapping.

CROSS-REFERENCE

This application is a continuation of U.S. Non-Provisional applicationSer. No. 16/930,614, filed Jul. 16, 2020, which is a continuation ofU.S. Non-Provisional application Ser. No. 16/339,048, filed Apr. 3,2019, which issued as U.S. Pat. No. 10,743,246 on Aug. 11, 2020, whichis the National Stage entry under 35 U.S.C. § 371 of Patent CooperationTreaty Application PCT/US2017/055511, filed Oct. 6, 2017, which claimsthe benefit of U.S. Provisional Application No. 62/405,451, filed onOct. 7, 2016; U.S. Provisional Application No. 62/418,360, filed Nov. 7,2016; and U.S. Provisional Application No. 62/501,808, filed May 5,2017, the contents of which are hereby incorporated by reference intheir entirety.

BACKGROUND

A wireless transmit/receive unit (WTRU) may be configured to operate ina 5G network. Depending on WTRU capabilities and the deploymentscenario, the WTRU may or may not move between various cells of the 5Gnetwork. Mobility rules and procedures for 5G networks may be used tosupport WTRUs associated with various levels of mobility while balancingthe amount of processing to be performed by the WTRU and the amount ofcontrol signaling exchanged with the network.

SUMMARY

One or more examples as described more fully below provide apparatuses,functions, procedures, processes, execution of computer programinstruction tangibly embodying a computer readable memory, functions andoperation of methods for one or more of the following. Systems, methods,and instrumentalities are disclosed for enforcing limited mobility in amobile network. A WTRU may receive a list that indicates one or moremappings between physical cell IDs (PCIs) of one or more neighbor cellsand an area identification (AID) for the one or more neighbor cells. TheWTRU may determine whether a target cell is in an allowed area or arestricted area using the list. For example, after receiving themappings of PCIs to AIDs, the WTRU may identify the PCI of a neighborcell, for example, by receiving the primary synchronization signal (PSS)and secondary synchronization signal (SSS) of the neighbor cell. TheWTRU may determine whether the WTRU is allowed to camp on and/or connectto the neighbor cell by determining the AID for the neighbor cell usingthe detected PCI for the neighbor cell and the PCI to AID mappinginformation.

A WTRU may generate a local list of unallowed cells, for example, sothat the WTRU can avoid selecting (e.g., repeatedly selecting) anunallowed cell. A WTRU may determine a maximum number of cell selectionattempts, for example, to limit cell selection attempts. A WTRU mayinitiate a timer to control the restart of cell selection attempts.

During operation, a mobility restriction area may become mismatchedbetween a WTRU and the network. The WTRU may attempt to establish a userplane when in a non-allowed area (e.g., a restricted area). The WTRU mayupdate a list of non-allowed areas. For example, the WTRU may update thelist of non-allowed areas in response to receiving a service rejectmessage from the network. A WTRU may move to a restricted area. Forexample, a WTRU in an inactive state may move to a restricted area. TheWTRU may indicate to the network that the WTRU has moved to therestricted area. The network may indicate a state change for the WTRU.The WTRU may add a registration area (e.g., a current registration area)in response to receiving a service reject message from the network. TheWTRU may add the registration area in the list of non-allowed areasand/or forbidden areas.

A WTRU may determine a PCI for a neighboring cell. The WTRU may receivea PCI to AID mapping list from the network. The WTRU may determine thatthe neighboring cell is in a restricted area using the PCI to AIDmapping list. For example, the WTRU may identify the AID associated withthe PCI of the neighboring cell using the PCI to AID mapping list. TheWTRU may determine whether the identified AID is associated with therestricted area. The WTRU may exclude the neighboring cell from a cellselection candidate set, for example, based on the determination thatthe neighboring cell is in the restricted area. The WTRU may notconsider the neighboring cell as a handover target, for example, basedon the determination that the neighboring cell is in the restrictedarea. The WTRU may generate a local restricted area list that includesone or more cells in the restricted area.

Systems, methods, and instrumentalities are disclosed for enforcinglimited mobility in a mobile network. For example, a wirelesstransmit/receive unit (WTRU) may receive (e.g., receive from a network)a mapping of physical cell identifications (PCIs) to areaidentifications (AIDs). The WTRU may determine a first PCI associatedwith a first neighbor cell. The WTRU may determine, based on the firstPCI and the PCIs to AIDs mapping, whether the WTRU is allowed to accessthe first neighbor cell. The WTRU may perform cell selection orreselection with the first neighbor cell as a cell selection orreselection candidate. The WTRU may perform cell selection orreselection based on the WTRU determining that the WTRU is allowed toaccess the first neighbor cell. The WTRU may determine that the WTRU isallowed to access the first neighbor cell based on the first PCI and thePCIs to AIDs mapping.

The WTRU may determine a second PCI associated with a second neighborcell. The WTRU may determine, based on the second PCI and the PCIs toAIDs mapping, whether the WTRU is allowed to access the second neighborcell. The WTRU may exclude the second neighbor cell from being the cellselection or reselection candidate based on determining that the WTRU isnot allowed to access the second neighbor cell based on the second PCIand the PCIs to AIDs mapping.

The WTRU may save an indication that the first and/or second neighborcell is excluded from being the cell selection or reselection candidate.The first and/or second neighbor cell may be excluded from being thecell selection or reselection candidate based on determining that theWTRU is not allowed to access the first neighbor cell based on the firstPCI and the PCIs to AIDs mapping. The indication may be saved local tothe WTRU.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a system diagram illustrating an example communicationssystem in which one or more disclosed examples may be implemented.

FIG. 1B is a system diagram illustrating an example wirelesstransmit/receive unit (WTRU) that may be used within the communicationssystem illustrated in FIG. 1A.

FIG. 1C is a system diagram illustrating an example radio access network(RAN) and an example core network (CN) that may be used within thecommunications system illustrated in FIG. 1A.

FIG. 1D is a system diagram illustrating a further example RAN and afurther example CN that may be used within the communications systemillustrated in FIG. 1A.

FIG. 2 is a messaging chart depicting an example restricted mobilityenforcement.

FIG. 3 is a messaging chart depicting an example restricted mobilityenforcement.

FIG. 4 depicts an example mapping of neighboring cell physical cellidentification (ID) to area identification (AID).

FIG. 5 depicts an example filtering of cells in a restricted area usinga physical cell ID to area ID mapping list.

FIG. 6 depicts an example construction of a local restricted cell list.

FIG. 7 depicts an example failed cell selection attempt timer andre-attempt timer.

FIG. 8 depicts an example update of a non-allowed area based onreceiving a reject message from the network.

FIG. 9 depicts an example WTRU switching to idle after moving to arestricted area.

FIG. 10 depicts an example WTRU signaling to the network that it is in arestricted area.

DETAILED DESCRIPTION

A detailed description of illustrative examples will now be describedwith reference to the various Figures. Although this descriptionprovides a detailed example of possible implementations, it should benoted that the details are intended to be exemplary and in no way limitthe scope of the application.

FIG. 1A is a diagram illustrating an example communications system 100in which one or more disclosed examples may be implemented. Thecommunications system 100 may be a multiple access system that providescontent, such as voice, data, video, messaging, broadcast, etc., tomultiple wireless users. The communications system 100 may enablemultiple wireless users to access such content through the sharing ofsystem resources, including wireless bandwidth. For example, thecommunications systems 100 may employ one or more channel accessmethods, such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailunique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM(UW-OFDM), resource block-filtered OFDM, filter bank multicarrier(FBMC), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a RAN104/113, a CN 106/115, a public switched telephone network (PSTN) 108,the Internet 110, and other networks 112, though it will be appreciatedthat the disclosed examples may contemplate any number of WTRUs, basestations, networks, and/or network elements. Each of the WTRUs 102 a,102 b, 102 c, 102 d may be any type of device configured to operateand/or communicate in a wireless environment. By way of example, theWTRUs 102 a, 102 b, 102 c, 102 d, any of which may be referred to as a“station” and/or a “STA”, may be configured to transmit and/or receivewireless signals and may include a user equipment (UE), a mobilestation, a fixed or mobile subscriber unit, a subscription-based unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watchor other wearable, a head-mounted display (HMD), a vehicle, a drone, amedical device and applications (e.g., remote surgery), an industrialdevice and applications (e.g., a robot and/or other wireless devicesoperating in an industrial and/or an automated processing chaincontexts), a consumer electronics device, a device operating oncommercial and/or industrial wireless networks, and the like. Any of theWTRUs 102 a, 102 b, 102 c and 102 d may be interchangeably referred toas a UE.

The communications systems 100 may also include a base station 114 aand/or a base station 114 b. Each of the base stations 114 a, 114 b maybe any type of device configured to wirelessly interface with at leastone of the WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to oneor more communication networks, such as the CN 106/115, the Internet110, and/or the other networks 112. By way of example, the base stations114 a, 114 b may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller,an access point (AP), a wireless router, and the like. While the basestations 114 a, 114 b are each depicted as a single element, it will beappreciated that the base stations 114 a, 114 b may include any numberof interconnected base stations and/or network elements.

The base station 114 a may be part of the RAN 104/113, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals on one or morecarrier frequencies, which may be referred to as a cell (not shown).These frequencies may be in licensed spectrum, unlicensed spectrum, or acombination of licensed and unlicensed spectrum. A cell may providecoverage for a wireless service to a specific geographical area that maybe relatively fixed or that may change over time. The cell may furtherbe divided into cell sectors. For example, the cell associated with thebase station 114 a may be divided into three sectors. Thus, in oneexample, the base station 114 a may include three transceivers, i.e.,one for each sector of the cell. In an example, the base station 114 amay employ multiple-input multiple output (MIMO) technology and mayutilize multiple transceivers for each sector of the cell. For example,beamforming may be used to transmit and/or receive signals in desiredspatial directions.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet(UV), visible light, etc.). The air interface 116 may be establishedusing any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104/113 and the WTRUs 102 a,102 b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 116 using wideband CDMA (WCDMA). WCDMAmay include communication protocols such as High-Speed Packet Access(HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink(DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).

In an example, the base station 114 a and the WTRUs 102 a, 102 b, 102 cmay implement a radio technology such as Evolved UMTS Terrestrial RadioAccess (E-UTRA), which may establish the air interface 116 using LongTerm Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro(LTE-A Pro).

In an example, the base station 114 a and the WTRUs 102 a, 102 b, 102 cmay implement a radio technology such as NR Radio Access, which mayestablish the air interface 116 using New Radio (NR).

In an example, the base station 114 a and the WTRUs 102 a, 102 b, 102 cmay implement multiple radio access technologies. For example, the basestation 114 a and the WTRUs 102 a, 102 b, 102 c may implement LTE radioaccess and NR radio access together, for instance using dualconnectivity (DC) principles. Thus, the air interface utilized by WTRUs102 a, 102 b, 102 c may be characterized by multiple types of radioaccess technologies and/or transmissions sent to/from multiple types ofbase stations (e.g., a eNB and a gNB).

In an example, the base station 114 a and the WTRUs 102 a, 102 b, 102 cmay implement radio technologies such as IEEE 802.11 (i.e., WirelessFidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability forMicrowave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, an industrialfacility, an air corridor (e.g., for use by drones), a roadway, and thelike. In an example, the base station 114 b and the WTRUs 102 c, 102 dmay implement a radio technology such as IEEE 802.11 to establish awireless local area network (WLAN). In an example, the base station 114b and the WTRUs 102 c, 102 d may implement a radio technology such asIEEE 802.15 to establish a wireless personal area network (WPAN). In yetan example, the base station 114 b and the WTRUs 102 c, 102 d mayutilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A,LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown inFIG. 1A, the base station 114 b may have a direct connection to theInternet 110. Thus, the base station 114 b may not be required to accessthe Internet 110 via the CN 106/115.

The RAN 104/113 may be in communication with the CN 106/115, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. The data may have varying qualityof service (QoS) requirements, such as differing throughputrequirements, latency requirements, error tolerance requirements,reliability requirements, data throughput requirements, mobilityrequirements, and the like. The CN 106/115 may provide call control,billing services, mobile location-based services, pre-paid calling,Internet connectivity, video distribution, etc., and/or performhigh-level security functions, such as user authentication. Although notshown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or theCN 106/115 may be in direct or indirect communication with other RANsthat employ the same RAT as the RAN 104/113 or a different RAT. Forexample, in addition to being connected to the RAN 104/113, which may beutilizing a NR radio technology, the CN 106/115 may also be incommunication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also serve as a gateway for the WTRUs 102 a, 102 b,102 c, 102 d to access the PSTN 108, the Internet 110, and/or the othernetworks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) and/orthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired and/or wireless communications networksowned and/or operated by other service providers. For example, thenetworks 112 may include another CN connected to one or more RANs, whichmay employ the same RAT as the RAN 104/113 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities (e.g., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks). For example, the WTRU 102 c shown in FIG. 1A may be configuredto communicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an example WTRU 102. As shownin FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad 128, non-removable memory 130, removable memory 132,a power source 134, a global positioning system (GPS) chipset 136,and/or other peripherals 138, among others. It will be appreciated thatthe WTRU 102 may include any sub-combination of the foregoing elements.

The processor 118 may be a general-purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in an example, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In an example, the transmit/receive element122 may be an emitter/detector configured to transmit and/or receive IR,UV, or visible light signals, for example. In an example, thetransmit/receive element 122 may be configured to transmit and/orreceive both RF and light signals. It will be appreciated that thetransmit/receive element 122 may be configured to transmit and/orreceive any combination of wireless signals.

Although the transmit/receive element 122 is depicted in FIG. 1B as asingle element, the WTRU 102 may include any number of transmit/receiveelements 122. More specifically, the WTRU 102 may employ MIMOtechnology. Thus, in an example, the WTRU 102 may include two or moretransmit/receive elements 122 (e.g., multiple antennas) for transmittingand receiving wireless signals over the air interface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In examples, the processor 118 may access informationfrom, and store data in, memory that is not physically located on theWTRU 102, such as on a server or a home computer (not shown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of a suitable location-determinationmethod.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs and/or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, a Virtual Reality and/or Augmented Reality (VR/AR) device, anactivity tracker, and the like. The peripherals 138 may include one ormore sensors, the sensors may be one or more of a gyroscope, anaccelerometer, a hall effect sensor, a magnetometer, an orientationsensor, a proximity sensor, a temperature sensor, a time sensor; ageolocation sensor; an altimeter, a light sensor, a touch sensor, amagnetometer, a barometer, a gesture sensor, a biometric sensor, and/ora humidity sensor.

The WTRU 102 may include a full duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for both the UL (e.g., for transmission) anddownlink (e.g., for reception) may be concurrent and/or simultaneous.The full duplex radio may include an interference management unit 139 toreduce and or substantially eliminate self-interference via eitherhardware (e.g., a choke) or signal processing via a processor (e.g., aseparate processor (not shown) or via processor 118). In an example, theWRTU 102 may include a half-duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for either the UL (e.g., for transmission) or thedownlink (e.g., for reception)).

FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106according to an example. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the CN 106.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an example. The eNode-Bs 160 a, 160 b, 160 cmay each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In an example, theeNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus, theeNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and/or receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160 a, 160 b, 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the UL and/or DL, and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160 b, 160 c may communicate with one another over an X2 interface.

The CN 106 shown in FIG. 1C may include a mobility management entity(MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN)gateway (or PGW) 166. While each of the foregoing elements are depictedas part of the CN 106, it will be appreciated that any of these elementsmay be owned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the eNode-Bs 162 a, 162 b, 162 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 162 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aserving gateway during an initial attach of the WTRUs 102 a, 102 b, 102c, and the like. The MME 162 may provide a control plane function forswitching between the RAN 104 and other RANs (not shown) that employother radio technologies, such as GSM and/or WCDMA.

The SGW 164 may be connected to each of the eNode Bs 160 a, 160 b, 160 cin the RAN 104 via the S1 interface. The SGW 164 may generally route andforward user data packets to/from the WTRUs 102 a, 102 b, 102 c. The SGW164 may perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink (DL) data isavailable for the WTRUs 102 a, 102 b, 102 c, managing and storingcontexts of the WTRUs 102 a, 102 b, 102 c, and the like.

The SGW 164 may be connected to the PGW 166, which may provide the WTRUs102 a, 102 b, 102 c with access to packet-switched networks, such as theInternet 110, to facilitate communications between the WTRUs 102 a, 102b, 102 c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may provide the WTRUs 102 a, 102 b, 102 c withaccess to circuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. For example, the CN 106 may include,or may communicate with, an IP gateway (e.g., an IP multimedia subsystem(IMS) server) that serves as an interface between the CN 106 and thePSTN 108. In addition, the CN 106 may provide the WTRUs 102 a, 102 b,102 c with access to the other networks 112, which may include otherwired and/or wireless networks that are owned and/or operated by otherservice providers.

Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, itis contemplated that in examples such a terminal may use (e.g.,temporarily or permanently) wired communication interfaces with thecommunication network.

In examples, the other network 112 may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an AccessPoint (AP) for the BSS and one or more stations (STAs) associated withthe AP. The AP may have an access or an interface to a DistributionSystem (DS) or another type of wired/wireless network that carriestraffic in to and/or out of the BSS. Traffic to STAs that originatesfrom outside the BSS may arrive through the AP and may be delivered tothe STAs. Traffic originating from STAs to destinations outside the BSSmay be sent to the AP to be delivered to respective destinations.Traffic between STAs within the BSS may be sent through the AP, forexample, where the source STA may send traffic to the AP and the AP maydeliver the traffic to the destination STA. The traffic between STAswithin a BSS may be considered and/or referred to as peer-to-peertraffic. The peer-to-peer traffic may be sent between (e.g., directlybetween) the source and destination STAs with a direct link setup (DLS).In examples, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS(TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP,and the STAs (e.g., all of the STAs) within or using the IBSS maycommunicate directly with each other. The IBSS mode of communication maysometimes be referred to herein as an “ad-hoc” mode of communication.

When using the 802.11ac infrastructure mode of operation or a similarmode of operations, the AP may transmit a beacon on a fixed channel,such as a primary channel. The primary channel may be a fixed width(e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.The primary channel may be the operating channel of the BSS and may beused by the STAs to establish a connection with the AP. In examples,Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may beimplemented, for example in in 802.11 systems. For CSMA/CA, the STAs(e.g., every STA), including the AP, may sense the primary channel. Ifthe primary channel is sensed/detected and/or determined to be busy by aSTA, the STA may back off. One STA (e.g., only one station) may transmitat any given time in a given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel forcommunication, for example, via a combination of the primary 20 MHzchannel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHzwide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz,and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may beformed by combining contiguous 20 MHz channels. A 160 MHz channel may beformed by combining 8 contiguous 20 MHz channels, or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. For the 80+80 configuration, the data, after channelencoding, may be passed through a segment parser that may divide thedata into two streams. Inverse Fast Fourier Transform (IFFT) processing,and time domain processing, may be done on each stream separately. Thestreams may be mapped on to the two 80 MHz channels, and the data may betransmitted by a transmitting STA. At the receiver of the receiving STA,the above described operation for the 80+80 configuration may bereversed, and the combined data may be sent to the Medium Access Control(MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. Thechannel operating bandwidths, and carriers, are reduced in 802.11af and802.11ah relative to those used in 802.11n, and 802.11ac. 802.11afsupports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space(TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and16 MHz bandwidths using non-TVWS spectrum. In an example, 802.11ah maysupport Meter Type Control/Machine-Type Communications, such as MTCdevices in a macro coverage area. MTC devices may have certaincapabilities, for example, limited capabilities including support for(e.g., only support for) certain and/or limited bandwidths. The MTCdevices may include a battery with a battery life above a threshold(e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channelbandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include achannel which may be designated as the primary channel. The primarychannel may have a bandwidth equal to the largest common operatingbandwidth supported by all STAs in the BSS. The bandwidth of the primarychannel may be set and/or limited by a STA, from among all STAs inoperating in a BSS, which supports the smallest bandwidth operatingmode. In the example of 802.11ah, the primary channel may be 1 MHz widefor STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.Carrier sensing and/or Network Allocation Vector (NAV) settings maydepend on the status of the primary channel. If the primary channel isbusy, for example, due to a STA (which supports only a 1 MHz operatingmode), transmitting to the AP, the entire available frequency bands maybe considered busy even though a majority of the frequency bands remainsidle and may be available.

In the United States, the available frequency bands, which may be usedby 802.11ah, are from 902 MHz to 928 MHz. In Korea, the availablefrequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the availablefrequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidthavailable for 802.11ah is 6 MHz to 26 MHz depending on the country code.

FIG. 1D is a system diagram illustrating an example RAN 113 and CN 115.As noted above, the RAN 113 may employ an NR radio technology tocommunicate with the WTRUs 102 a, 102 b, 102 c over the air interface116. The RAN 113 may also be in communication with the CN 115.

The RAN 113 may include gNBs 180 a, 180 b, 180 c, though it will beappreciated that the RAN 113 may include any number of gNBs. The gNBs180 a, 180 b, 180 c may each include one or more transceivers forcommunicating with the WTRUs 102 a, 102 b, 102 c over the air interface116. In an example, the gNBs 180 a, 180 b, 180 c may implement MIMOtechnology. For example, gNBs 180 a, 108 b may utilize beamforming totransmit signals to and/or receive signals from the gNBs 180 a, 180 b,180 c. Thus, the gNB 180 a, for example, may use multiple antennas totransmit wireless signals to, and/or receive wireless signals from, theWTRU 102 a. In an example, the gNBs 180 a, 180 b, 180 c may implementcarrier aggregation technology. For example, the gNB 180 a may transmitmultiple component carriers to the WTRU 102 a (not shown). A subset ofthese component carriers may be on unlicensed spectrum while theremaining component carriers may be on licensed spectrum. In an example,the gNBs 180 a, 180 b, 180 c may implement Coordinated Multi-Point(CoMP) technology. For example, WTRU 102 a may receive coordinatedtransmissions from gNB 180 a and gNB 180 b (and/or gNB 180 c).

The WTRUs 102 a, 102 b, 102 c may communicate with gNBs 180 a, 180 b,180 c using transmissions associated with a scalable numerology. Forexample, the OFDM symbol spacing and/or OFDM subcarrier spacing may varyfor different transmissions, different cells, and/or different portionsof the wireless transmission spectrum. The WTRUs 102 a, 102 b, 102 c maycommunicate with gNBs 180 a, 180 b, 180 c using subframe or transmissiontime intervals (TTls) of various or scalable lengths (e.g., containingvarying number of OFDM symbols and/or lasting varying lengths ofabsolute time).

The gNBs 180 a, 180 b, 180 c may be configured to communicate with theWTRUs 102 a, 102 b, 102 c in a standalone configuration and/or anon-standalone configuration. In the standalone configuration, WTRUs 102a, 102 b, 102 c may communicate with gNBs 180 a, 180 b, 180 c withoutalso accessing other RANs (e.g., such as eNode-Bs 160 a, 160 b, 160 c).In the standalone configuration, WTRUs 102 a, 102 b, 102 c may utilizeone or more of gNBs 180 a, 180 b, 180 c as a mobility anchor point. Inthe standalone configuration, WTRUs 102 a, 102 b, 102 c may communicatewith gNBs 180 a, 180 b, 180 c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102 a, 102 b, 102 c may communicatewith/connect to gNBs 180 a, 180 b, 180 c while also communicatingwith/connecting to another RAN such as eNode-Bs 160 a, 160 b, 160 c. Forexample, WTRUs 102 a, 102 b, 102 c may implement DC principles tocommunicate with one or more gNBs 180 a, 180 b, 180 c and one or moreeNode-Bs 160 a, 160 b, 160 c substantially simultaneously. In thenon-standalone configuration, eNode-Bs 160 a, 160 b, 160 c may serve asa mobility anchor for WTRUs 102 a, 102 b, 102 c and gNBs 180 a, 180 b,180 c may provide additional coverage and/or throughput for servicingWTRUs 102 a, 102 b, 102 c.

Each of the gNBs 180 a, 180 b, 180 c may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in the ULand/or DL, support of network slicing, dual connectivity, interworkingbetween NR and E-UTRA, routing of user plane data towards User PlaneFunction (UPF) 184 a, 184 b, routing of control plane informationtowards Access and Mobility Management Function (AMF) 182 a, 182 b andthe like. As shown in FIG. 1D, the gNBs 180 a, 180 b, 180 c maycommunicate with one another over an Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182 a, 182 b,at least one UPF 184 a, 184 b, at least one Session Management Function(SMF) 183 a, 183 b, and possibly a Data Network (DN) 185 a, 185 b. Whileeach of the foregoing elements are depicted as part of the CN 115, itwill be appreciated that any of these elements may be owned and/oroperated by an entity other than the CN operator.

The AMF 182 a, 182 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N2 interface and may serve as acontrol node. For example, the AMF 182 a, 182 b may be responsible forauthenticating users of the WTRUs 102 a, 102 b, 102 c, support fornetwork slicing (e.g., handling of different PDU sessions with differentrequirements), selecting a particular SMF 183 a, 183 b, management ofthe registration area, termination of NAS signaling, mobilitymanagement, and the like. Network slicing may be used by the AMF 182 a,182 b to customize CN support for WTRUs 102 a, 102 b, 102 c based on thetypes of services being utilized WTRUs 102 a, 102 b, 102 c. For example,different network slices may be established for different use cases suchas services relying on ultra-reliable low latency (URLLC) access,services relying on enhanced massive mobile broadband (eMBB) access,services for machine type communication (MTC) access, and/or the like.The AMF 162 may provide a control plane function for switching betweenthe RAN 113 and other RANs (not shown) that employ other radiotechnologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP accesstechnologies such as WiFi.

The SMF 183 a, 183 b may be connected to an AMF 182 a, 182 b in the CN115 via an N11 interface. The SMF 183 a, 183 b may also be connected toa UPF 184 a, 184 b in the CN 115 via an N4 interface. The SMF 183 a, 183b may select and control the UPF 184 a, 184 b and configure the routingof traffic through the UPF 184 a, 184 b. The SMF 183 a, 183 b mayperform other functions, such as managing and allocating UE IP address,managing PDU sessions, controlling policy enforcement and QoS, providingdownlink data notifications, and the like. A PDU session type may beIP-based, non-IP based, Ethernet-based, and the like.

The UPF 184 a, 184 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N3 interface, which may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between the WTRUs 102a, 102 b, 102 c and IP-enabled devices. The UPF 184, 184 b may performother functions, such as routing and forwarding packets, enforcing userplane policies, supporting multi-homed PDU sessions, handling user planeQoS, buffering downlink packets, providing mobility anchoring, and thelike.

The CN 115 may facilitate communications with other networks. Forexample, the CN 115 may include, or may communicate with, an IP gateway(e.g., an IP multimedia subsystem (IMS) server) that serves as aninterface between the CN 115 and the PSTN 108. In addition, the CN 115may provide the WTRUs 102 a, 102 b, 102 c with access to the othernetworks 112, which may include other wired and/or wireless networksthat are owned and/or operated by other service providers. In anexample, the WTRUs 102 a, 102 b, 102 c may be connected to a local DataNetwork (DN) 185 a, 185 b through the UPF 184 a, 184 b via the N3interface to the UPF 184 a, 184 b and an N6 interface between the UPF184 a, 184 b and the DN 185 a, 185 b.

In view of FIGS. 1A-1D, and the corresponding description of FIGS.1A-1D, one or more, or all, of the functions described herein withregard to one or more of: WTRU 102 a-d, Base Station 114 a-b, eNode-B160 a-c, MME 162, SGW 164, PGW 166, gNB 180 a-c, AMF 182 a-ab, UPF 184a-b, SMF 183 a-b, DN 185 a-b, and/or any other device(s) describedherein, may be performed by one or more emulation devices (not shown).The emulation devices may be one or more devices configured to emulateone or more, or all, of the functions described herein. For example, theemulation devices may be used to test other devices and/or to simulatenetwork and/or WTRU functions.

The emulation devices may be designed to implement one or more tests ofother devices in a lab environment and/or in an operator networkenvironment. For example, the one or more emulation devices may performthe one or more, or all, functions while being fully or partiallyimplemented and/or deployed as part of a wired and/or wirelesscommunication network in order to test other devices within thecommunication network. The one or more emulation devices may perform theone or more, or all, functions while being temporarilyimplemented/deployed as part of a wired and/or wireless communicationnetwork. The emulation device may be directly coupled to another devicefor purposes of testing and/or may performing testing using over-the-airwireless communications.

The one or more emulation devices may perform the one or more, includingall, functions while not being implemented/deployed as part of a wiredand/or wireless communication network. For example, the emulationdevices may be utilized in a testing scenario in a testing laboratoryand/or a non-deployed (e.g., testing) wired and/or wirelesscommunication network in order to implement testing of one or morecomponents. The one or more emulation devices may be test equipment.Direct RF coupling and/or wireless communications via RF circuitry(e.g., which may include one or more antennas) may be used by theemulation devices to transmit and/or receive data.

A 5G network may enable customizable mobility support. For example, a 5Gnetwork may enable customizable mobility support based on a WTRU'smobility capabilities, characteristics, applications, and/or services. A5G network may enable one or more (e.g., different) levels of mobilitysupport. In this manner, the network may configure WTRUs to implementdifferent and/or customized mobility procedures depending on themobility level assigned to the WTRU and/or the corresponding mobilityrestrictions associated with different cells.

The levels of mobility support may include a no mobility level. In theno mobility level, the WTRU may be configured to remain static orquasi-static. In the no mobility level, the WTRU may (e.g., may only)access the network via a fixed access point. If the WTRU accesses (e.g.,only accesses) the network via a fixed access point, the tracking area(TA) of the WTRU may not change.

The levels of mobility support may include a low mobility level. In thelow mobility level, the WTRU may be configured to move (e.g., may beexpected to move) within a predefined geographical area and/or anexpected geographical area. For example, in the low mobility level, theWTRU may move (e.g., may be expected to move) within a list of TAs for acampus.

The levels of mobility support may include a full mobility level. In thefull mobility level, the WTRU may be configured to be allowed to moveacross one or more geographic areas. For example, in the full mobilitylevel, the WTRU may randomly move across one or more geographic areasand/or may not be generally restricted from moving into othergeographical areas.

In the low mobility level, movement of the WTRU may be restricted. Forexample, in the low mobility level, movement of the WTRU may berestricted to be within a predefined geographical area. The low mobilitylevel may be referred to as a limited mobility level and/or a restrictedmobility level.

A WTRU mobility level may be determined by the core network. Forexample, a WTRU mobility level may be determined by the core networkbased on information, such as WTRU subscriptions, WTRU capabilities,WTRU location, and/or network policies. A WTRU mobility level may bechanged. For example, a WTRU mobility level may be changed based on oneor more of a subscription change, a location change, and/or a policychange.

The core network may configure one or more areas to be associated with amobility restriction for a WTRU. For example, the core network mayconfigure one or more cells to be considered one or more of an allowedarea, a non-allowed area, and/or a forbidden area for a WTRU.

In an allowed area, the WTRU may be permitted to initiate communicationwith the network. In an allowed area, the WTRU may be permitted toinitiate communication with the network using the control plane (CP)and/or the user plane (UP). The WTRU may be permitted to initiatecommunication with the network, as allowed by the subscription.

In a forbidden area, the WTRU may not be permitted to initiatecommunication (e.g., any communication) with the network. For example,in a forbidden area, the WTRU may not be permitted to initiatecommunication with the network using the CP or the UP.

In a non-allowed area, the WTRU may not be allowed to initiate sessionmanagement (SM) signaling, but may be allowed to initiate other types ofsignaling. For example, in a non-allowed area, the WTRU may not bepermitted to initiate session management (SM) signaling to obtain userservices, but in a non-allowed area, the WTRU may be allowed to initiatemobility management signaling. For example, in a non-allowed area, theWTRU may initiate mobility management signaling so that the network mayupdate (e.g., be able to update) the allowed area list, the forbiddenarea list, etc. The WTRU may initiate mobility management signaling sothat the network may track (e.g., be able to track) stolen equipment,etc.

A type of area restriction may take precedence over another type of arearestriction. For example, the forbidden area may take precedence overthe allowed area and/or the non-allowed area.

In addition to the terms allowed area, non-allowed area, and forbiddenarea, the term restricted area may be used to represent a non-allowedarea and/or a forbidden area. For example, the term restricted area mayrefer to both a non-allowed area and a forbidden area when notdifferentiating between the non-allowed area and the forbidden area.

The configuration of an allowed area and/or a restricted area mayinclude a list of area identifications. For example, the configurationof an allowed area and/or a restricted area may include a list of areaidentifications (AIDs). Example of AIDs may include Tracking AreaIdentifications (TAIs), Global Cell Identifications (GCIs), and/or thelike. The AIDs (e.g., each of the AIDs) may be associated with a givenmobility restriction (e.g., allowed, non-allowed, forbidden, etc.).

The network may enforce a limited mobility or a restricted mobility of aWTRU. For example, the network may enforce a limited mobility or arestricted mobility of a WTRU when the WTRU is configured with anallowed area or a restricted area.

A WTRU may be configured with one or more allowed and/or restrictedareas. The WTRU may be aware of where the WTRU may obtain service orwhere the WTRU may not obtain service. For example, the WTRU may beaware of where the WTRU may obtain service or where the WTRU may notobtain service, based on one or more of the configured allowed and/orrestricted areas. The WTRU may determine whether the WTRU is in anallowed area or in a restricted area. For example, the WTRU maydetermine whether the WTRU is in an allowed area or in a restrictedarea, based on one or more area identifications (e.g., current areaidentifications). The one or more area identifications (e.g., currentarea identifications) may be broadcasted. For example, the one or morearea identifications (e.g., current area identifications) may bebroadcasted in the System Information (SI) from the network. The WTRUmay match the one or more area identifications (e.g., current areaidentifications) against one or more configured allowed and/orrestricted areas. For example, the WTRU may match the one or more areaidentifications (e.g., current area identifications) against one or moreconfigured allowed and/or restricted areas of the WTRU. If the WTRUdetermines that the WTRU is in a restricted area, the WTRU may refrainfrom initiating a service request.

FIG. 2 depicts an example restricted mobility enforcement.

As shown in 206, the WTRU 202 may be configured with one or more allowedand/or restricted areas. The WTRU 202 may be configured with one or moreallowed and/or restricted areas via pre-configuration, Open MobileAlliance (OMA) Device Management procedures, and/or Mobility Managementsignaling procedures.

When WTRU 202 is configured with the allowed and/or restricted areas,the WTRU 202 may determine whether WTRU 202 is in a restricted areafaster than another entity. For example, when WTRU 202 is configuredwith the allowed and/or restricted areas, the WTRU 202 may determinewhether WTRU 202 is in a restricted area faster than the network 204.When WTRU 202 is configured with the allowed and/or restricted areas,the WTRU 202 may determine whether WTRU 202 is in a restricted areawithout a signaling exchange with the Network 204. When the WTRU 202 isconfigured with the allowed and/or restricted areas, the WTRU 202 mayrefrain from initiating MO requests (e.g., unnecessary MO requests). Forexample, the WTRU 202 may not initiate an unnecessary MO request, whichmay fail.

The WTRU 202 may attempt to camp on allowed areas. For example, the WTRU202 may attempt to camp on allowed areas when the WTRU 202 is assigned amobility level of low mobility or limited mobility. The WTRU 202 mayattempt to camp on allowed areas as much as possible. The WTRU 202 mayavoid selecting or reselecting cells that belong to restricted areas.

The WTRU 202 may determine whether the WTRU is in an allowed orrestricted area after reading System Information. For example, when WTRU202 is configured with the allowed and/or restricted areas, the WTRU 202may determine whether WTRU is in an allowed or restricted area afterreading System Information. WTRU 202 may read system information afterthe WTRU 202 has selected a cell and has camped on the cell. If the WTRU202 is in a restricted area, the WTRU 202 may stay in a cell in therestricted area (e.g., the wrong cell) without service or the WTRU 202may reselect to another cell (e.g., a correct cell). Reading SystemInformation of a wrong cell may waste time and/or resources. The WTRU202 may determine whether a target cell is in an allowed or restrictedarea before camping on the target cell.

A network, such as network 204, may enforce limited mobility orrestricted mobility on the WTRU 202. The network 204 may enforce limitedmobility or restricted mobility on the WTRU 202 when the WTRU 202 isconfigured with one or more allowed or restricted areas. The network 204may enforce limited mobility or restricted mobility on the WTRU 202 whenthe WTRU 202 is not configured with one or more allowed or restrictedareas.

The one or more allowed or restricted areas may be configured on thenetwork side. For example, the one or more allowed or restricted areasmay be configured on the network side and not configured in the WTRU.The one or more allowed or restricted areas may be configured in WTRUsubscription data and/or in WTRU mobility context. As shown in 208, theNetwork 204 may provide system information to the WTRU 202. The systeminformation may include WTRU information. For example, the systeminformation may include WTRU subscription data. The system informationmay include network information. The system information may include AreaID information.

WTRU 202 may enter a new area, as shown in 210. When WTRU 202 enters anew area, WTRU 202 may not know whether WTRU 202 is in an allowed areaor a restricted area. For example, WTRU 202 may not know whether WTRU202 is in an allowed area or a restricted area until WTRU 202 initiatesmobile originating (MO) signaling. MO signaling may include an AreaUpdate, an Area ID, and/or a Service Request. As shown in 212, the WTRU202 may determine whether the WTRU 202 is in an allowed area or arestricted area. For example, as shown in 212, the WTRU 202 maydetermine whether the WTRU 202 is in an allowed area or a restrictedarea by comparing the Area ID against allowed and/or restricted areas,as shown in 216. The WTRU 202 may compare the Area ID against configuredallowed and/or restricted areas.

If WTRU 202 is in an allowed area, MO signaling may be successful. Forexample, if the WTRU 202 is in an allowed area, a service request may besent from WTRU 202 to Network 204, as shown in 218. If the WTRU 202 isin a restricted area, the MO signaling may be rejected by Network 204.For example, if the WTRU 202 is in a restricted area, the MO signalingmay be rejected by Network 204 with an indication that WTRU 204 is in arestricted area. If WTRU 202 is in a restricted area, WTRU 202 mayrefrain from initiating MO signaling, as shown in 214.

The WTRU may not be configured with the allowed and/or restricted areas(e.g., allowed and/or restricted area information). When a WTRU is notconfigured with the allowed and/or restricted areas, the WTRU may beunable to determine whether the WTRU is in an allowed or restrictedarea. For example, the WTRU may be unable to determine whether the WTRUis in an allowed or restricted area before the WTRU's MO request isrejected by the network.

A WTRU may avoid camping on a restricted cell. For example, a WTRU mayavoid camping on a restricted cell before the WTRU reads SystemInformation and/or sends a MO request. The WTRU may avoid camping on arestricted cell before reading System Information and/or sending a MOrequest to reduce delay. For example, the WTRU may avoid camping on arestricted cell before reading System Information and/or sending a MOrequest to reduce the delay of cell selection/reselection and/or toenable efficient power consumption. A restricted cell may be a cell in arestricted area.

The WTRU may camp on a restricted cell and/or may attempt to reselect toanother cell. If the WTRU camps on a restricted cell and/or attempts toreselect to another cell, a next target cell may be in an allowed areaor the next target cell may not be in an allowed area. The WTRU mayreselect (e.g., continue reselecting, such as circling around) one ormore cells in restricted areas. For example, WTRU may continuereselecting one or more wrong cells.

The WTRU may be configured to avoid selecting (e.g., repeatedlyselecting) wrong cells.

The serving RAN and/or WTRU may select a target cell for handover. Forexample, during handover, the serving RAN and/or WTRU may select a besttarget cell) for handover. The serving RAN may control the target cellselection. The configuration of restricted areas may be unavailable inthe RAN. The serving RAN may (e.g., may incorrectly) hand over WTRU to acell. For example, the serving RAN may (e.g., may incorrectly) hand overWTRU to a cell in a restricted area. In WTRU controlled handover, WTRUmay be unable to determine whether the target cell is restricted or isunrestricted. For example, in WTRU controlled handover, WTRU may beunable to determine whether the target cell is restricted or isunrestricted before the WTRU accesses the target cell and/or reading thetarget cell's System Information (SI).

During operation, a mismatch may occur to the mobility restriction areamaintained at the WTRU and/or maintained at the network. For example,knowledge of mobility restriction, non-allowed areas, and/or forbiddenareas at the WTRU may be different from the non-allowed areas configuredfor that WTRU at the network. As an example, a network configuration maybe updated by the network without notifying the WTRU. The mobilityrestriction area, non-allowed area, and/or forbidden area may bemismatched between the WTRU and the network when network reconfiguresthe mobility restriction area. For example, the mobility restrictionarea, non-allowed area, and/or forbidden area may be mismatched betweenthe WTRU and the network when network reconfigures the mobilityrestriction area while the WTRU is in idle mode. The WTRU may not benotified (e.g., may not be immediately notified) of a change in themobility restriction area. For example, the WTRU may not be notified ofa change in the mobility restriction area because the WTRU may be in anunreachable state and/or the network may desire to notify the WTRU ofthe change in the mobility restriction area when the WTRU transitions toa connected state.

The WTRU may be restricted from initiating signaling. For example, theWTRU may be restricted from initiating signaling to establish a datasession. The WTRU may be restricted from initiating signaling toestablish a data session when the WTRU is in a non-allowed area (e.g., arestricted area). The WTRU may initiate signaling to establish a datasession which may (e.g., should) be prevented. For example, the WTRU mayinitiate signaling to establish a data session which may (e.g., should)be prevented based on a configuration mismatch of a mobility arearestriction. WTRU and/or network actions may be performed to synchronizethe mobility restriction area. For example, the WTRU and/or networkactions may be performed to synchronize the mobility restriction areabetween the WTRU and the network in such scenarios.

An RRC INACTIVE state may be provided for a next generation WTRU and/orRAN. For example, an RRC INACTIVE state and/or IDLE and CONNECTED statesmay be provided for the next generation WTRU and/or RAN. A WTRU in theRRC INACTIVE state may behave like a WTRU in the IDLE state. Forexample, a WTRU in the RRC INACTIVE state may behave like a WTRU in theIDLE state to minimize the signaling activities and/or powerconsumption. A WTRU context may be maintained in the RAN and/or thenetwork control plane (CP) and user plane (UP) connections may be kept.For example, when the WTRU is in the RRC INACTIVE state, a WTRU contextmay be maintained in the RAN and/or the network CP and UP connectionsmay be kept. When a WTRU is in the RRC INACTIVE state, the WTRU'slocation may not be tracked by the core network (CN). When a WTRU is inthe RRC INACTIVE state, the WTRU's location may be tracked by the RAN.For example, the WTRU's location may be tracked by the RAN at cell levelor at “RAN notification/paging area” level. A WTRU in RRC INACTIVE statemay transition to CONNECTED state. For example, a WTRU in RRC INACTIVEstate may transition to CONNECTED state without a full RRCestablishment. The WTRU may begin transmitting data without performing astate transition.

A WTRU may be assigned a mobility level of Restricted Mobility. Forexample, a WTRU may be assigned a mobility level of Restricted Mobilityfor an IDLE state. When the WTRU transitions to CONNECTED state and(e.g., and then) to INACTIVE state, the mobility level may remain aRestricted Mobility. For example, a Restricted Mobility level assignedin idle mode may apply for the RRC INACTIVE state. For example, theWTRU's mobility behavior in the RRC INACTIVE state may follow (e.g.,mostly follow) that in IDLE state. The CN may determine a WTRU that hastransitioned from the CONNECTED state to the RRC INACTIVE state to be inthe CONNECTED state. The DL data may be forwarded (e.g., continue to beforwarded) to RAN. The RAN may not be able (e.g., allowed) to deliverthe DL data to the WTRU when the WTRU is in the restricted area.

A network may provide information relating to one or more restrictedcells. The information relating to restricted cells may be identified byPCIs and/or corresponding Area IDs. For example, the network may provide(e.g., to a WTRU) a list of restricted cells which may be identified byPCIs and/or corresponding Area IDs. The WTRU may determine whether acandidate or target cell is in an allowed or restricted area. Forexample, the WTRU may determine whether a candidate or target cell is inan allowed or restricted area before camping on the candidate or targetcell. The WTRU may read the System Information of the candidate ortarget cell and may avoid cell selection and/or SI reading.

A WTRU may be unable to determine whether a target cell is in an allowedarea or a restricted area. For example, the WTRU may be unable todetermine whether a target cell is in an allowed area or a restrictedarea because the area identifications (e.g., such as tracking areaidentifications (TAIs) or global cell IDs) that are used to configurethe allowed or restricted area list in the WTRU may be unrecognizable(e.g., not recognized) before the WTRU camps on the target cell. Areaidentifications may include a TAI, a global cell ID (GCI), and/or thelike. Network may determine whether a target cell is in an allowed areaor a restricted area. Network 304 may broadcast the areaidentifications. For example, network 304 may broadcast the areaidentifications in the network's System Information (e.g., SIB1 in LTE).The WTRU may be able to read (e.g., may only be able to read) the SystemInformation after the WTRU camps on the target cell.

FIG. 3 depicts an example restricted mobility enforcement with network304 configured with one or more allowed and/or restricted areas. Asshown by 306, WTRU 302 may register with network 304. Network 304 may beconfigured with the allowed and/or restricted areas, as shown by 308.For example, network 304 may retrieve the allowed and/or restrictedareas of WTRU 304 from subscription data.

The WTRU 302 may enter a new area, as shown in 310. For example, WTRU302 may enter an allowed area or a restricted area. WTRU 302 may notknow whether WTRU 302 has entered an allowed area or a restricted areawhen WTRU 302 enters a new area. For example, WTRU 302 may not knowwhether WTRU 302 has entered an allowed area or a restricted area untilWTRU 302 initiates mobile originating (MO) signaling. MO signaling mayinclude an Area Update, and Area ID, and/or a Service Request.

The WTRU 302 may send Network 304 an area update, as shown in 312. Thearea update may include an area ID of the WTRU 302. The area ID of theWTRU 202 may be the current area ID. The area ID of the WTRU 202 may beanother area ID (e.g., an adjacent area ID).

The Network 304 may determine whether the WTRU 302 is in an allowed areaor in a restricted area. For example, as shown in 314, Network 303 maydetermine whether the WTRU 302 is in an allowed area or in a restrictedarea by comparing the Area ID (e.g., current area ID) against an allowedarea and/or restricted area. For example, the Network 304 may comparethe current Area ID against configured allowed and/or restricted areas.

The Network 304 may prevent the WTRU 302 from connecting to a restrictedarea. For example, the Network 304 may prevent the WTRU 302 fromconnecting to the restricted area if the Network 304 determines that theWTRU 302 is in a restricted area. As shown in 318, if the Network 304determines that the WTRU 302 is in a restricted area, the Network 304may send WTRU 302 an area update reject message. The area update rejectmessage may include an indication of the rejection. For example, thearea update reject message may include an indication that the rejectionwas caused because the WTRU 302 attempted to enter a restricted area. Ifthe WTRU 302 receives an area update reject message, the WTRU 302 mayrefrain from initiating MO signaling, as shown in 320.

If Network 304 determines that the WTRU 302 is in a restricted area(e.g., forbidden area) the Network 403 may send an Area Update Rejectionmessage 318, for example, indicating the cause of the rejection was thatthe WTRU was in a restricted (e.g., forbidden) area. If the Network 304determines that the WTRU 302 is in an allowed area (e.g., not in arestricted area), the Network 304 may accept the WTRU's area updaterequest. For example, as shown in 322, if the Network 304 determinesthat the WTRU 302 is in an allowed area, the Network 304 may send WTRU302 an area update accept message. If the WTRU 302 receives an areaupdate accept, the WTRU 302 may initiate MO signaling or MO data, asshown in 324.

As described herein, the WTRU may receive one or more neighboring cellArea Identifications. FIG. 4 depicts an example mapping of physical cellIDs (e.g., PCIs of neighbor cells) to one or more mobility areas such asTAIs or GCIs. FIG. 4 depicts an example mapping of physical cell IDs(e.g., physical cell IDs relating to a neighboring cell) to global cellIDs and/or tracking area IDs (e.g., area IDs). One or more mappings maybe provided via a list. The list may include a mapping of the one ormore neighboring cell's physical cell ID to its area ID (e.g., such asGCI and/or TAI). For example, neighboring cells 402A, 402B, 402C, 402D(collectively referred to as 402) may be associated with respectivephysical cell IDs 404A, 404B, 404C, 404D (collectively referred to as404). Physical cell IDs 404A, 404B, 404C, 404D may be associated withrespective global cell-IDs or TAI IDs 406A, 406B, 406C, 406D(collectively referred to as 406). The Area Identification used in thelist may depend on what information (e.g., TAI or GCI) is used toconfigure the allowed or restricted area in the WTRU.

A WTRU may receive the list of mappings of neighboring cell physicalcell IDs to area IDs. The list of mappings may be broadcast by a servingRAN. For example, the list of mappings may be broadcast by a serving RANas part of System Information. A WTRU that supports limited mobility mayuse (e.g., require) the list of mappings. For example, a WTRU thatsupports limited mobility may use (e.g., require) the list of mappingswhen the WTRU accesses the serving RAN. The WTRU may delay reading thesystem information. For example, the WTRU may delay reading the list ofmappings (e.g., the list of mappings included in the systeminformation). The WTRU may delay reading the list of mappings (e.g., thelist of mappings included in the system information) until the WTRU isassigned to a limited mobility level.

The WTRU may receive the list of mappings from the serving RAN. Forexample, the WTRU may receive the list of mappings from the serving RANin dedicated RRC messages. The serving RAN may indicate that a list ofmappings of neighboring cell physical cell IDs to area IDs is available.For example, the serving RAN may indicate that a list of mappings ofneighboring cell physical cell IDs to area IDs is available by includinga flag in the broadcast system information. The WTRU may send a RRCrequest message to the serving RAN for the list of mappings. The WTRUmay request (e.g., request via the RRC request message) the mappingsbetween neighboring cells' physical Cell IDs and Area IDs. The returnedlist of mappings may include mappings for allowed and/or restrictedcells.

The WTRU may indicate the WTRU's allowed and/or restricted Area IDs. Forexample, the WTRU may indicate the WTRU's allowed and/or restricted AreaIDs in a RRC request message. The serving RAN may return (e.g., may onlyreturn) the physical Cell IDs of the neighboring cells that are allowedand/or restricted.

The WTRU may request an update to the list of mappings. For example, theWTRU may request an update to the list of mappings when a WTRU moves tocamp on a new cell. The WTRU may request an update to the list ofmappings from the new serving RAN.

The WTRU may receive the list from the core network. For example, theWTRU may receive the list from the Mobility Management Function (e.g.,through Mobility Management signaling). The core network may include thetopology (e.g., full topology) of the network. For example, the corenetwork may include the topology (e.g., full topology) of the network,such that the core network may generate a list of mappings according tothe WTRU's location. The core network may query the serving RAN and/orOperation and Management (OAM) for the list of mappings. For example,the core network may query the serving RAN or OAM for the list ofmappings when the core network provides (e.g., needs to provide) thelist of mappings to the WTRU.

A limited mobility WTRU (e.g., a limited mobility WTRU in idle orconnected inactive mode) may check a candidate cell's physical Cell IDagainst a list. For example, with the list of mappings between PhysicalCell IDs (PCIs) and its Area IDs available, a limited mobility WTRU inidle or connected inactive mode may check a candidate cell's physicalCell ID against the list of mappings. A limited mobility WTRU in idle orconnected inactive mode may check a candidate cell's physical Cell IDagainst the list of mappings before determining to camp on the candidatecell. If the candidate cell's Cell ID is in the list, a correspondingArea ID may be available from the list. The WTRU may check thecorresponding Area ID against the WTRU's local configuration of allowedor restricted area list. If the candidate cell is in the restrictedarea, the WTRU may exclude the candidate cell from the candidate cellset for cell selection or reselection ranking evaluation.

A limited mobility level WTRU in connected mode may check the candidatecell's physical Cell ID against the list. For example, a limitedmobility level WTRU in connected mode may check the candidate cell'sphysical Cell ID against the list before selecting a target cell forhandover. If a candidate cell is in the restricted area, the WTRU maychoose not to include the measurement of the candidate cell in therestricted area in a measurement report. In WTRU autonomous handovercontrol, the WTRU may exclude the candidate cell in the restricted areafrom being a handover target.

FIG. 5 depicts an example filtering of cells in a restricted area usinga mapping. The mapping may be a physical cell ID to area ID mapping. Thephysical cell ID to area ID mapping may be provided via a list (e.g., aphysical cell ID to area ID mapping list). At 500, the WTRU may identifya mapping. For example, the WTRU may receive and/or determine a list ormapping 504 that associates the PCIs with an AID, such as a GCI. TheWTRU may receive a list of PCIs associated with neighbour cells in thearea and the list may associate each PCI with one or more AIDs. Forexample, the AIDs may correspond to tracking areas and/or the receivedlist 504 may associate the PCIs of neighbour cells with TAIs. The AIDsmay correspond to GCIs and/or the list may associate the PCIs ofneighbour cells with the GCIs. The WTRU may have received mobilitymanagement signaling and/or may be configured with a list of allowedTAIs, a list of forbidden TAIs, and/or a list of not allowed TAIs (e.g.,and/or a list of allowed tracking area codes (TACs), a list of forbiddenTACs, and/or a list of not-allowed TACs). The WTRU may have receivedmobility management signaling and/or may be configured with a list ofallowed GCIs, a list of forbidden GCIs, and/or a list of not allowedGCIs.

For example, the neighboring cells may be scanned, at 502. For example,the neighboring cells may be scanned by a WTRU. The neighboring cellsmay include a physical cell ID (PCI), such as described herein. A listmapping the PCI and global cell ID (GCI) may be provided, at 504. Forexample, the network may provide a list mapping the PCI and the GCI. Thenetwork may provide a list mapping the PCI and the GCI to a WTRU.

An area ID may be determined. For example, the PCI in the mapping listmay be used to determine an area ID (e.g., a corresponding area ID), at506. The area ID may be a global ID (GCI), a TAI, or the like.

It may be determined whether the area ID (e.g., corresponding area ID)corresponds to a restricted area or an allowed area, at 508. Forexample, at 510, the WTRU may generate a local list of cells that havebeen determined to be in one or more restricted areas. The WTRU maygenerate a local restricted cell list based on the mobility level of theWTRU. The WTRU may generate a local restricted cell irrespective of themobility level that the WTRU is assigned to. For example, the WTRU maygenerate and/or update the local restricted cell list when the WTRU isassigned to a limited mobility level. The WTRU may generate and/orupdate the local restricted cell list when the WTRU is assigned to afull mobility level and/or a no mobility level (e.g., as long as theconfigured allowed or restricted area is available).

The WTRU may add the PCI and/or Area ID of the cell to the local list ofrestricted cells. For example, the WTRU may add the PCI and/or Area IDof the cell to the local list of restricted cells when the WTRU readsthe Area ID information from a cell's System Information. The WTRU mayadd the PCI and/or Area ID of the cell to the local list of restrictedcells when the WTRU reads the Area ID information from a cell's SystemInformation and determines that the cell is in the configured restrictedarea. At 508, the WTRU may check the PCI and/or Area ID of a candidateor target cell against the local list of restricted cells. For example,the WTRU may check the PCI and/or Area ID of a candidate or target cellagainst the local list of restricted cells when the WTRU is looking fora candidate or target cell for camping or handover. If the PCI and/orArea ID of the candidate or target cell is found in the local list ofrestricted cells, the WTRU may exclude the cell from the cellselection/reselection candidate set, at 514. For example, if the PCIand/or Area ID of the candidate or target cell is found in the locallist of restricted cells, the WTRU may exclude the cell from being acandidate camping cell and/or a handover target.

The WTRU may include a cell in the cell selection/reselection candidateset. For example, if the PCI and/or Area ID of the candidate or targetcell is not found in the local list of restricted cells, the WTRU mayinclude the cell in the cell selection/reselection candidate set, at512. If the PCI and/or Area ID of the candidate or target cell is notfound in the local list of restricted cells, the WTRU may determine thatthe candidate or target cell is an allowed cell. If the PCI and/or AreaID of the candidate or target cell is not found in the local list ofrestricted cells, the WTRU may allow the cell to be a candidate campingcell and/or a handover target.

A WTRU may generate a user interface presentation about the restrictedarea. For example, the WTRU may generate a user interface presentationabout the restricted area using the received mapping list. The WTRU maydetermine whether one or more neighboring cells are in the restrictedarea (e.g., by checking against this mapping list). If the WTRUdetermines that one or more neighboring cells are in the restricted area(e.g., by checking against this mapping list), the WTRU may warn a uservia a user interface. The WTRU may warn a user via a user interface sothat the user may decide not to move further (e.g., to avoid the risk oflosing service). The WTRU may generate a map to indicate which cellsand/or areas around the user are allowed or restricted. The WTRU may usethe mapping list to generate the map.

FIG. 6 depicts an example construction of a local restricted cell list.At 602, a neighboring cell may be scanned. For example, the WTRU and/orNetwork may scan neighboring cells to acquire the PCIs of theneighboring cells. The WTRU and/or the Network may use one or more AreaIDs to acquire the PCIs of the neighboring cells. A PCI-GCI mapping listmay be received, at 604. For example, the WTRU may receive the PCI-CGImapping list from the network. The WTRU may review the mapping list. Forexample, the WTRU may review the mapping list and a PCI (e.g., a PCIcorresponding to an Area ID) may not be found in the mapping list, at606. The WTRU may review a local restricted cell list. The localrestricted cell list may contain one or more entries. The localrestricted cell list may be empty, at 612. The WTRU may review the localrestricted cell list and the WTRU may not identify a PCI in the localrestricted cell list, at 608.

A cell may be selected in which the WTRU may camp, at 610. For example,the WTRU may select a PCI of a cell in which the WTRU is to camp, at610. The WTRU may identify an Area ID. For example, the WTRU mayidentify an Area ID from System Information and the WTRU may select acell having a PCI that corresponds to the identified Area ID. The WTRUmay camp at the selected cell. At 614, it may be determined if theidentified Area ID is a restricted Area ID. For example, the WTRU maycheck the System Information to determine if the Area ID is a restrictedArea ID. If the Area ID is not a restricted Area ID (e.g., based on theSystem Information), the WTRU may camp on the cell, at 616. If the AreaID is a restricted Area ID (e.g., based on the System Information), thePCI and/or Area ID corresponding to the Area ID may be added to thelocal restricted cell list, at 618. The local restricted cell list maybe updated. At 620, the Area ID and corresponding PCI and/or GCI may beupdated in the local restricted cell list. For example, the Area ID andcorresponding PCI and/or GCI may be updated in the local restricted celllist to indicate that the WTRU is in a restricted area. The neighboringcells may be scanned and/or the PCI of the cells may be acquired, at602.

A network-configured allowed or restricted area list may be changed inthe WTRU. For example, the WTRU may compare the restricted cell list(e.g., the local restricted cell list) against the changed (e.g., new)allowed or restricted area list. The WTRU may update the localrestricted cell list based on the changed allowed or restricted arealist. For example, if a cell (e.g., PCI-1) is in the local restrictedcell list, and the cell's corresponding Area ID (AID-1) is in the oldrestricted area list and is not in the changed (e.g., new) restrictedarea list, the WTRU may remove the cell (e.g., PCI-1) from the localrestricted cell list.

A WTRU may use the local restricted cell list independent of a PCI-AreaID mapping list. For example, the WTRU may use the local restricted celllist independent of the WTRU receiving the PCI-Area ID mapping list fromthe network. If the local restricted cell list and the PCI-Area IDmapping list are available, the lists may have some common items (e.g.,PCIs). Information for a cell may not be aligned in the lists. Forexample, Area IDs may not be aligned in the lists. The local restrictedcell list may override the PCI-Area ID mapping list. The information inthe PCI-Area ID mapping list may be modified. For example, theinformation in the PCI-Area ID mapping list may be modified to match thelocal restricted cell list.

One or more restricted area terms may be used. For example, non-allowedarea and/or a forbidden area terms may be used, which may be restrictedareas. Non-allowed area and/or forbidden area terms may have differentrestrictions. For example, the Mobility Management signaling, such asArea Update, may be allowed in a non-allowed area and may not be allowedin a forbidden area. A WTRU may construct one or more restricted celllists. A (e.g., each of the) restricted cell list may correspond to oneor more restricted area definitions.

A WTRU may be configured with a maximum number of failed cell selectionand/or reselection attempts. For example, the WTRU may be configuredwith a maximum number of failed cell selection and/or reselectionattempts to avoid repeated selection of restricted cells (e.g., due tomobility restriction). The WTRU may camp on a selected cell and the WTRUmay determine that the selected cell is in a restricted area. Forexample, the WTRU may determine that the selected cell is in arestricted area after the WTRU reads the System Information. When theWTRU determines that the selected cell is in a restricted area, acounter of the failed cell selection attempts may increase by 1. Whenthe counter reaches a predetermined number (e.g., a maximum number), theWTRU may perform an action. For example, when the counter reaches apredetermined number (e.g., a maximum number), the WTRU may stop (e.g.,temporarily stop) attempting to select a cell and the WTRU may remainout of service. If the WTRU selects a cell in an allowed area, thecounter may be reset.

The WTRU may start a re-attempt timer. For example, the WTRU may start are-attempt timer when the counter reaches a number (e.g., a maximumnumber) of failed cell selection and/or reselection attempts. When there-attempt timer expires, the WTRU may restart attempting cellselection.

The network may configure the number (e.g., maximum number) of failedcell selection and/or reselection attempts. For example, the network mayconfigure the number (e.g., maximum number) of failed cell selectionand/or reselection attempts via NAS signaling. The network may configurethe number (e.g., maximum number) of failed cell selection and/orreselection attempts when the WTRU is assigned to a limited mobilitylevel. The network may configure the re-attempt timer. For example, thenetwork may configure the re-attempt timer via NAS signaling. Thenetwork may configure the re-attempt timer when the WTRU is assigned toa limited mobility level.

The WTRU may be in a restricted area and/or the WTRU may not bereachable. The WTRU may inform the network if the WTRU is in therestricted area and/or whether the WTRU may not be reachable. Forexample, if a WTRU is in a restricted area and cannot reselect to anallowed area, the WTRU may inform the network that the WTRU is in therestricted area and/or that the WTRU may not be reachable. The WTRU mayinitiate a NAS signaling (e.g., a special NAS signaling). For example,the WTRU may initiate a NAS signaling to inform the network that theWTRU is in the restricted area and/or that the WTRU may not bereachable. The network may not reject the special NAS signaling. Forexample, the network may not reject the special NAS signaling due tomobility restriction. The network may record the information in the WTRUcontext and/or may propagate the information to one or more (e.g.,necessary) CN nodes. The one or more CN nodes may include the UPgateways (GWs) that may be serving the WTRU. The network may suspend oneor more of the WTRU's packet data network (PDN) connections.

FIG. 7 depicts an example failed cell selection attempt timer andre-attempt timer. A cell PCI may be selected. For example, at 702, acell PCI may be selected for a cell in which the WTRU may camp. The AreaID of the selected cell may be read. For example, the WTRU may select acell in which the WTRU is to camp. The WTRU may read the Area ID of theselected cell. For example, the WTRU may read the Area ID from SystemInformation.

It may be determined if the Area ID corresponding to the selected cellis in a restricted area, at 704. For example, a WTRU may determine ifthe Area ID corresponding to the selected cell PCI is in a restrictedarea. If the Area ID is not in a restricted area, a counter may be setto zero, at 708. If the Area ID is in a restricted area, the counter maybe incremented (e.g., incremented by 1), at 706, and it may bedetermined if the counter has reached a maximum value, at 710. If thecounter has not reached a maximum value, a cell PCI (e.g., another cellPCI) may be selected for which the WTRU may camp and the correspondingArea ID may be read from SI, at 702.

If the counter reaches a maximum value, at 710, cell selection attemptsmay be stopped, at 712. For example, the WTRU may stop selecting cells.At 714, a re-attempt timer may be started. For example, if the counterhas reached a maximum value, the WTRU may start a re-attempt timer afterthe WTRU stops cell selection attempts. The re-attempt timer may bestarted after a predetermined time from the WTRU stopping cell selectionattempts.

A WTRU may reset and/or refresh an allowed area list. A WTRU may resetand/or refresh an unallowed area list. The WTRU may delete one or moreof the PCIs, GCIs, and/or TAIs and/or associated mappings when the WTRUrefreshes the allowed or unallowed area list. The WTRU may request anupdated list of allowed or unallowed areas from the network. The WTRUmay generate an updated list of allowed or unallowed areas. For example,the WTRU may generate an updated list of allowed or unallowed areasbased on information from the network, as described herein.

A WTRU may refresh an area list. For example, a WTRU may refresh an arealist when the WTRU detaches from the network. The WTRU may refresh thearea list when the network initiates a detach and/or when the WTRUinitiates a detach. The WTRU may refresh the area list when implicitlydetaching from the network. The WTRU may generate an updated area list.For example, the WTRU may generate an updated area list upon reattachingto the network.

A WTRU may refresh an area list when the WTRU moves into a newgeographic location. For example, a WTRU moving into a new geographiclocation may trigger a new attach and/or an area update with theinformation associated with the new geographic location. The network maypush new area configuration information to the WTRU. For example, thenetwork may push new area configuration information to the WTRU based onthe information associated with the new geographic location.

A WTRU may refresh an area list when the WTRU receives a predefinedcause code from the network. For example, in response to a NAS mobilitymanagement or session management message, a WTRU may refresh an arealist when the WTRU receives a predefined cause code from the network.The WTRU may update or reset the area list. For example, the WTRU mayupdate or reset the area list upon the WTRU receiving the predefinedcause code from the network. The network may send the predefined causecode when the WTRU sends a NAS message. For example, the network maysend the predefined cause code when the WTRU sends a normal and/or aperiodic TAU with new WTRU capability (such as switching from MO onlytransmission mode to bidirectional transmission mode). The network maysend the predefined cause code when a session management message and/ora procedure is executed. The session management message and/or proceduremay update WTRU session continuity behavior. For example, the sessionmanagement message and/or procedure may update WTRU session continuitybehavior such that the WTRU may be configured for a different SSC(session continuity) mode (e.g., changing from SSC mode 2 to SSC 3). Thenetwork may send the predefined cause code when WTRU subscriptioninformation changes. For example, the network may send the predefinedcause code when WTRU subscription information changes in relation tomobility level support. A change to WTRU subscription information maycause the network to update the mobility level, and the network may senda NAS message (e.g., a mobility management or session managementmessage) with the predefined cause code. The network may send thepredefined cause code when the network receives information from a3^(rd) party application server. The information from the 3^(rd) partyapplication server may indicate to modify the mobility level of the WTRUand/or modify the area where the WTRU is permitted to perform limitedmobility. The network may expose the network capability to the 3^(rd)party application servers. For example, the network may expose thenetwork capability to the 3^(rd) party application servers via thecapability exposure function.

A WTRU and/or the core network may provide information about the allowedand/or unallowed list to the RAN (e.g., RAN node). For example, the WTRUand/or the core network may inform the RAN that the allowed or unallowedlist has been reset and/or updated. A WTRU message may not be rejectedby the RAN. For example, the WTRU message may not be rejected by the RANif the RAN is aware of the change in the allowed or unallowed area list.The RAN may configure an area for which the WTRU operates in RANinactive state. For example, the RAN may configure an area for which theWTRU may operate in RAN inactive state using the allowed or unallowedarea list.

The RAN may send predefined cause code information. For example, the RANmay send predefined cause code information via an RRC message. Thepredefined cause code information may reset and/or update the allowed orunallowed list. For example, the predefined cause code information mayreset and/or update the allowed or unallowed list at the WTRU. Thepredefined cause code information may be sent by the RAN upon receivingthe allowed/unallowed area information from the core network. The RRClayer in the WTRU may interact with the NAS layer to inform the RANabout a reset and/or update in the list. For example, the RRC layer inthe WTRU may interact with the NAS layer to inform the RAN about a resetand/or update in the list when the WTRU receives the allowed orunallowed list from the RAN. Cross layer information sharing may preventthe NAS layer from generating signaling messages. For example, crosslayer information sharing may prevent the NAS layer from generatingsignaling messages if the WTRU is operating in an unallowed area.

A mobility restriction area mismatch may occur between a WTRU and anetwork. For example, conditions may lead to a mobility restriction areamismatch occurring between a WTRU and a network. The WTRU may enter anon-allowed area. The WTRU may be unaware that the WTRU entered anon-allowed area. For example, a WTRU may enter a non-allowed area whenthe WTRU is in an idle mode and the WTRU may be unaware that the WTRUentered a non-allowed area. The WTRU may attempt to establish a userplane in the non-allowed area. A non-allowed area may include arestricted area, an unallowed area, and/or a forbidden area. Forexample, the WTRU may attempt to establish a user plane by sending aregistration message and/or a service request message. The registrationmessage may be a Tracking Area Update and/or a registration requestmessage with a user plane indication (e.g., an active flag).

The WTRU may include an active flag, one or more PDU session IDs, and/orone or more other indications. The active flag, one or more PDU sessionIDs, and/or one or more other indications may be sent to the network.The active flag, one or more PDU session IDs, and/or one or more otherindications may be sent to the network in a registration requestmessage. For example, the WTRU may include an active flag, one or morePDU session ID(s), and/or one or more other indications in theregistration request message sent to the network to establish user planebearers as part of the registration. The WTRU may send the registrationrequest message to an AMF in the network. The network may reject theregistration request message. For example, the network may reject theregistration request message when the network receives the registrationrequest message with a user plane establishment indication and thenetwork is aware that the WTRU is in the non-allowed area. The networkmay send a reject message (e.g., a registration reject message) that mayinclude a predefined cause code. For example, the network may send areject message (e.g., a registration reject message) that may include apredefined cause code to describe the reason for the rejection. Thereason for rejection may include the area being not allowed and/orforbidden. When the network receives the registration request messagewith a user plane establishment indication and the network is aware thatthe WTRU is in the non-allowed area, the network may accept theregistration request message. For example, the network may accept theregistration request message and the network may not establish the userplane bearers. The network may update the list of allowed andnot-allowed areas. For example, the network may update the list ofallowed and not-allowed areas in a registration accept message.

The WTRU may add a registration area to the list of non-allowed areas orforbidden areas. For example, the WTRU may add a current registrationarea to the list of non-allowed areas or forbidden areas when the WTRUreceives a registration accept or reject message from the network. TheWTRU may not include an indication to establish a user plane in furtherregistration messages (e.g., periodic registration). For example, theWTRU may not include an indication to establish a user plane in furtherregistration messages (e.g., periodic registration) while the WTRU is inthe current area (e.g., in a non-allowed or forbidden area).

The WTRU may send a second registration message without the user planeindication. For example, the WTRU may send a second registration messagewithout the user plane indication if the WTRU receives a registrationreject message with a cause code indicating a non-allowed area. The WTRUmay update the list of non-allowed areas on the WTRU.

FIG. 8 depicts an example update of a non-allowed area based onreceiving a reject message from a network (e.g., a network entity). Theexample update may be based on receiving a reject message from an AMF(Access and Mobility Management Function) of the network entity. A WTRU802 may be in an idle mode. For example, the WTRU 802 may enter anon-allowed area, at 806, when the WTRU 802 is in an idle mode. The WTRU802 may have user plane data. WTRU 802 may attempt to establish a userplane using a Service Request message or a TAU, at 808. The WTRU 802 maysend a Service Request message and/or a TAU to Network entity 804 (e.g.,AMF of the Network entity). For example, the WTRU 802 may send a ServiceRequest (SR) message and/or a TAU to the Network entity 804. The WTRU802 may send a Service Request (SR) message and/or a TAU to the Networkentity 804 so that the WTRU 802 may come out of an idle state while theWTRU 802 is in the non-allowed area. The WTRU 802 may send a ServiceRequest message and/or a TAU so that the WTRU 802 may come out of anidle state while the WTRU 802 is in the non-allowed area if the WTRU 802is unaware that the current area has been reconfigured by the networkentity to be a non-allowed area or forbidden area.

The network entity 804 may reject the Service request message and/orTAU, at 810. The Network entity 804 may include a predefined cause codeand/or an area list in the service reject message when the Networkentity 804 rejects the Service request message and/or TAU. The Networkentity 804 may include a predefined cause code in the service rejectmessage because the WTRU 802 may be unaware that the WTRU 802 is in thenon-allowed area. The cause code may indicate a reason for the servicerejection. An example reason may include a user plane being not allowed(e.g., the WTRU is in a non-allowed area and/or a forbidden area). Thearea list may be a reconfigured area list that indicates one or moreallowed areas, non-allowed areas, and/or forbidden areas.

The tracking area (e.g., the current tracking area) may be added to thelist of non-allowed areas, at 812. For example, WTRU 802 may add thecurrent tracking area to the list of non-allowed areas. At 814, aService Request message and/or a TAU may be sent. For example, a ServiceRequest message and/or a TAU may be sent without an indication toestablish the User Plane. The Service Request message and/or TAU may besent from the WTRU 802 to the Network entity 804, at 816. The ServiceRequest message and/or TAU may be sent from the WTRU 802 to the Networkentity 804 without an indication to establish a user plane.

The network (e.g., network entity) may send a predefined cause codeand/or an area list in the service accept message. For example, thenetwork may send a predefined cause code and/or an area list in theservice accept message if a WTRU sends a service request message (e.g.,a NAS service request message) in response to paging by the network. Thenetwork may not establish a user plane. For example, the network may notestablish a user plane if requested by the WTRU. The WTRU may determinethat the WTRU is in a non-allowed area. The network may establish (e.g.,only establish) a control plane based on the request from the WTRU. Forexample, the WTRU may determine that the WTRU is in a non-allowed areabased on the network not establishing a user plane in response to aservice request message.

The WTRU may add the current registration area to a list of non-allowedareas and/or forbidden areas. For example, the WTRU may add the currentregistration area to a list of non-allowed areas and/or forbidden areaswhen the WTRU receives a service accept or service reject message. TheWTRU may not include an indication to establish a user plane (e.g.,include PDU session IDs) in other service request registration messages.For example, the WTRU may not include an indication to establish a userplane (e.g., include PDU session IDs) in other service requestregistration messages when the WTRU is in the current area.

The WTRU may send one or more service request messages without the userplane indication (e.g., PDU session IDs). For example, the WTRU may senda service request message without the user plane indication (e.g., PDUsession IDs) if the WTRU receives a service reject message. The WTRU mayreceive a service reject message in response to a service requestmessage. The service request message may be sent in response to networkpaging.

The WTRU may perform a registration. For example, the WTRU may perform aregistration to update the WTRU's list of allowed and/or non-allowedareas. The WTRU may perform a registration to update the WTRU's list ofallowed and/or non-allowed areas when the WTRU receives a service acceptor service reject message.

The WTRU may initiate a Tracking Area Update and/or a Registrationupdate. For example, the WTRU may initiate a Tracking Area Update and/ora Registration update when the WTRU enters an area which is configuredas allowed or non-allowed area and at the network side has been changedto a forbidden area. The WTRU may receive a TAU Reject and/or aRegistration Reject message with an indication (e.g., a predefined causecode) that the area is forbidden. The WTRU may add the area to aconfigured forbidden area list and/or the WTRU may update the WTRU'sallowed area or non-allowed area. The TAU Reject and/or RegistrationReject message may include an updated list of allowed areas, non-allowedareas, and/or forbidden areas. The WTRU may update one or more localconfigurations with the updated lists of allowed areas, non-allowedareas, and/or forbidden areas.

The WTRU may not include one or more PDU session IDs and/or a user planeindication similar to an active flag (e.g., when sending a registrationupdate). For example, the WTRU may not include one or more PDU sessionIDs and/or a user plane indication similar to an active flag (e.g., whensending a registration update) when the WTRU is in the non-allowed area.For example, when the WTRU is aware that the WTRU is in a non-allowedarea, the WTRU may not include one or more PDU session IDs (e.g., whensending Service request message) and/or a user plane indication similarto an active flag (e.g., when sending registration update).

A WTRU may move into a restricted area. For example, a WTRU in an RRCINACTIVE state may move from an allowed area to a restricted area.

The WTRU may determine whether the WTRU is in an allowed area or arestricted area. For example, if the WTRU was assigned a RestrictedMobility level (e.g., before entering an RRC INACTIVE state), the WTRUmay determine whether the WTRU is in an allowed area or a restrictedarea. The WTRU may determine whether the WTRU is in an allowed area or arestricted area when the WTRU is in the RRC INACTIVE state and the WTRUenters a new cell or area. If the WTRU determines that the WTRU is in arestricted area, the WTRU may switch (e.g., immediately switch) to anRRC IDLE state. The WTRU may switch (e.g., immediately switch) to an RRCIDLE state without any RRC signaling (e.g., explicit RRC signaling)between the WTRU and the Network (NW) and/or RAN. A state switch fromthe RRC INACTIVE state to the IDLE state may be transparent to the RANand/or Network. For example, the RAN and/or Network may maintain theWTRU context and/or CP/UP connection following the state switch.

The RAN may attempt to reach the WTRU. For example, the RAN may attemptto reach the WTRU following a state switch. The RAN may attempt to reachthe WTRU by paging and/or sending a notification. For example, the RANmay attempt to reach the WTRU by paging and/or sending a notificationvia a physical layer signal. The WTRU may not respond to the RAN'sattempt to reach the WTRU. The WTRU may not respond to the paging and/orthe notification. The RAN may remove the WTRU context and/or mayinitiate the NG2 connection release. For example, based on no responsefrom the WTRU, the RAN may remove the WTRU context and/or may initiatethe NG2 connection release.

FIG. 9 is a messaging chart depicting an example WTRU 902 switching toan idle state after moving to a restricted area. The WTRU may move backto an allowed area after the WTRU has switched to the IDLE state. TheWTRU may move back to an allowed area before, or after, the RAN removesthe WTRU context. If the WTRU moves back to an allowed area before theRAN removes the WTRU context, there may be a discrepancy between theWTRU and the RAN/CN in terms of the WTRU's RRC state.

As shown at 908, the WRU may be in an RRC_INACTIVE state (e.g., anRRC_INACTIVE mode). The RAN 904 and the CN 906 may perform a CP/UPconnection, at 910. For example, the RAN 904 and the CN 906 may performa CP/UP connection when the WTRU 902 is in the RRC_INACTIVE state. TheWTRU 902 may have switched to an IDLE state while the RAN 904 determineswhether the WTRU 902 is in an RRC INACTIVE state. The discrepancy may beresolved. For example, the discrepancy may be resolved when the WTRU 902in IDLE state initiates an RRC connection establishment towards the RAN904, and the WTRU 902 and the RAN 904 switched to full CONNECTED modebased on the RRC connection establishment.

The WTRU 902 may move to a restricted cell, at 912. The WTRU 902 maymove to a restricted cell (e.g., area) and/or the WTRU 902 may switch toidle mode. The WTRU 902 may remain in an INACTIVE state and the WTRU 902may send a signal to the RAN 904 indicating that the WTRU 902 is in arestricted area. The WTRU 902 may send the signal to the RAN 904proactively or in response to the RAN's paging or notification. Forexample, CN 906 may send downlink (DL) data to the RAN 904, at 914. TheRAN 904 may send a paging or a notification to the WTRU 902, as shown in916. The RAN 904 may send a paging or a notification to the WTRU 902,based on the RAN 904 receiving the DL data. The WTRU 902 may send thesignal to the RAN 904 indicating that the WTRU 902 is in a restrictedarea, based on the WTRU 902 receiving the RAN's paging or notification.

A timer may be set. For example, a timer may be set by the RAN node 904.The timer may expire if the response to the paging or notificationmessage is not received from the WTRU 902 within a predetermined time,as shown in 918. The CP connection may be released. For example, the CPconnection may be released, at 920, if the timer expires. The WTRUcontext may be removed, at 922. For example, the WTRU context may beremoved if the CP connection is released.

The WTRU 902 may remain in an INACTIVE state and the WTRU may send asignal to the RAN. The signal may indicate that the WTRU is in arestricted area. The WTRU may send the signal to the RAN proactively orthe WTRU may send the signal to the RAN in response to the RAN's pagingor notification.

The RAN may command the WTRU to remain in an INACTIVE state ortransition to an IDLE state. For example, the RAN may command the WTRUto remain in an INACTIVE state or transition to an IDLE state based onreceiving the signal indicating that the WTRU is in a restricted area.

The RAN may request the WTRU to enter an IDLE state. For example, whenthe RAN requests the WTRU to enter an IDLE state, the RAN may remove oneor more (e.g., any) local WTRU context and/or may release the NG2control plane connection.

The RAN may request the WTRU to remain in an INACTIVE state. When theRAN requests the WTRU to enter an IDLE state, the RAN may initiate a PDUsession suspension. For example, the RAN may initiate a PDU sessionsuspension through the existing CP connection. The RAN may initiate aPDU session suspension through the existing CP connection such that theCN will not forward the downlink data to the RAN. The CN may bufferand/or drop the incoming downlink data.

When the WTRU moves back to an allowed area and the WTRU's state is anINACTIVE state, the WTRU may send a signal to the RAN indicating thatthe WTRU is in an allowed area. The RAN may initiate one or more CNprocedures to resume the WTRU's PDU connection. For example, the RAN mayinitiate one or more CN procedures to resume the WTRU's PDU connectionthat was previously suspended).

FIG. 10 is a messaging chart depicting an example WTRU signaling to thenetwork that the WTRU is in a restricted area. The WTRU 1002 may be inan RRC_INACTIVE state (e.g., RRC_INACTIVE mode), as shown in 1008. TheRAN 1004 and the CN 1006 may perform a CP/UP connection, at 1010. Forexample, the RAN 1004 and the CN 1006 may perform a CP/UP connectionwhen the WTRU 1002 is in the RRC_INACTIVE state. The CN 1006 may send apaging or notification. For example, the CN 1006 may send a paging ornotification to RAN 1004, at 1012. The WTRU 1002 may move to arestricted cell (e.g., restricted area), at 1014. The WTRU 1002 may senda signal to the RAN 1004. For example, the WTRU 1002 may send a signalto the RAN 1004, at 1016. The signal may indicate that the WTRU 1002 isin a restricted cell.

One or more actions may occur, based on the RAN 1004 receiving thesignal from the WTRU 1002. For example, the WTRU 1002 may switch to anidle mode (e.g., option 1, as shown on FIG. 10 ). The RAN 1004 mayindicate to the WTRU 1002 for the WTRU 1002 to switch to an idle mode,at 1018. For example, the indication may be a state command from the RAN1004 to the WTRU 1002. The RAN 1004 may indicate to the CN 1006 torelease the CP connection, at 1020. The WTRU context may be removed, at1022.

The WTRU 1002 may remain in inactive mode (e.g., option 2, as shown onFIG. 10 ). The RAN 1004 may indicate to WTRU 1002 for the WTRU 1002 toremain in an inactive mode, at 1024. For example, the indication may bea state command from the RAN 1004 to the WTRU 1002. The RAN 1004 mayindicate to the CN 1006 to suspend the PDU connection, at 1026.

The WTRU may remain in an INACTIVE state and may initiate a NASprocedure (e.g., to suspend the WTRU's PDU connections). The RAN may betransparent to the NAS procedure. Although a WTRU may not (e.g., shouldnot) initiate a NAS signaling from a restricted area, the Network maynot reject the PDU session suspension request (e.g., make it anexception).

The WTRU may move back to an allowed area. When the WTRU moves back toan allowed area and the WTRU is in an INACTIVE state, the WTRU mayinitiate a NAS procedure to resume the suspended PDU connections.

Although features and elements are described above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. In addition, the methods described hereinmay be implemented in a computer program, software, or firmwareincorporated in a computer-readable medium for execution by a computeror processor. Examples of computer-readable media include electronicsignals (transmitted over wired or wireless connections) andcomputer-readable storage media. Examples of computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom access memory (RAM), a register, cache memory, semiconductormemory devices, magnetic media such as internal hard disks and removabledisks, magneto-optical media, and optical media such as CD-ROM disks,and digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for usein a WTRU, WTRU, terminal, base station, RNC, or any host computer.

What is claimed:
 1. A method implemented by a network node, the methodcomprising: receiving a registration request message from a wirelesstransmit receive unit (WTRU); determining that the WTRU has moved to alocation based on the registration request message; determining one ormore of an allowed area or a non-allowed area for the WTRU based on thedetermined location into which the WTRU has moved; and sending aregistration accept message to the WTRU, the registration accept messageindicating the one or more of the allowed area or the non-allowed area.2. The method of claim 1, wherein, in the non-allowed area the WTRU isnot allowed to initiate session management (SM) signaling for user datatransmission.
 3. The method of claim 1, wherein the registration requestmessage comprises a tracking area update message.
 4. The method of claim1, wherein the registration request message comprises an indication ofthe location of the WTRU.
 5. The method of claim 1, wherein the networknode comprises an access and mobility management function (AMF).
 6. Anetwork node comprising a processor and memory, the processor and memoryconfigured to: receive a registration request message from a wirelesstransmit receive unit (WTRU); determine that the WTRU has moved to alocation based on the registration request message; determine one ormore of an allowed area or a non-allowed area for the WTRU based on thedetermined location into which the WTRU has moved; and send aregistration accept message to the WTRU, the registration accept messageindicating the one or more of the allowed area or the non-allowed area.7. The network node of claim 6, wherein, in the non-allowed area theWTRU is not allowed to initiate session management (SM) signaling foruser data transmission.
 8. The network node of claim 6, wherein theregistration request message comprises a tracking area update message.9. The network node of claim 6, wherein the registration request messagecomprises an indication of the location of the WTRU.
 10. The networknode of claim 6, wherein the network node comprises an access andmobility management function (AMF).
 11. A wireless transmit/receive unit(WTRU) comprising a processor and memory, the processor and memoryconfigured to: send a registration request message to a network node,wherein the WTRU is configured with one or more of a first allowed areaor a first non-allowed area when the registration request message issent to the network node; receive a registration accept message from thenetwork node, the registration accept message indicating one or more ofa second allowed area or a second non-allowed area, wherein the secondallowed area or the second non-allowed area is indicated to the WTRUbased on a change in location of the WTRU.
 12. The WTRU of claim 1,wherein, in the non-allowed area the WTRU is not allowed to initiatesession management (SM) signaling for user data transmission.
 13. TheWTRU of claim 1, wherein the registration request message comprises atracking area update message.
 14. The WTRU of claim 1, wherein theregistration request message comprises an indication of the location ofthe WTRU.
 15. The WTRU of claim 1, wherein the network node comprises anaccess and mobility management function (AMF).